home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / a_man / cat1 / chkutent.z / chkutent
Encoding:
Text File  |  1998-10-20  |  8.1 KB  |  133 lines
  1.  
  2.  
  3.  
  4. cccchhhhkkkkuuuutttteeeennnntttt((((1111MMMM))))                                                      cccchhhhkkkkuuuutttteeeennnntttt((((1111MMMM))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _cccc_hhhh_kkkk_uuuu_tttt_eeee_nnnn_tttt - check and repair utmp entries
  10.  
  11. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      _cccc_hhhh_kkkk_uuuu_tttt_eeee_nnnn_tttt _[[[[_----_ffff _uuuu_tttt_mmmm_pppp_xxxx_----_ffff_iiii_llll_eeee_]]]]_[[[[_----_wwww _wwww_tttt_mmmm_pppp_xxxx_----_ffff_iiii_llll_eeee_]]]]
  13.  
  14. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  15.      _cccc_hhhh_kkkk_uuuu_tttt_eeee_nnnn_tttt opens and reads _////_vvvv_aaaa_rrrr_////_aaaa_dddd_mmmm_////_uuuu_tttt_mmmm_pppp_xxxx and makes 2 checks for
  16.      consistency; whether there are any entries that have duplicate 'id'
  17.      fields, and whether there are any entries that are stale.  Stale entries
  18.      are found by looking at all entries that have _uuuu_tttt______tttt_yyyy_pppp_eeee equal to
  19.      _UUUU_SSSS_EEEE_RRRR______PPPP_RRRR_OOOO_CCCC_EEEE_SSSS_SSSS and checking to see if the process (specified by _uuuu_tttt______pppp_iiii_dddd) is
  20.      still alive.  If it isn't, it sets the _uuuu_tttt______tttt_yyyy_pppp_eeee to _DDDD_EEEE_AAAA_DDDD______PPPP_RRRR_OOOO_CCCC_EEEE_SSSS_SSSS and sets
  21.      the process's termination time to the current time.  It then makes sure
  22.      that the files _uuuu_tttt_mmmm_pppp, _wwww_tttt_mmmm_pppp, and _wwww_tttt_mmmm_pppp_xxxx are all consistent.
  23.  
  24.      Keeping the utmp file(s) consistent and up to date is important for
  25.      accounting, _llll_aaaa_ssss_tttt(1), and other system administration functions.  However,
  26.      these files are updated by a variety of programs, some of which are
  27.      public domain programs.  If these programs are terminated without giving
  28.      them the opportunity to clean up their _uuuu_tttt_mmmm_pppp entry, the files can easily
  29.      get out of sync.  The exact algorithm for updating the utmp files is also
  30.      notoriously non-standard, so many third party or public domain
  31.      applications may not quite do it correctly for IRIX.  For these reasons,
  32.      _cccc_hhhh_kkkk_uuuu_tttt_eeee_nnnn_tttt is run by _cccc_rrrr_oooo_nnnn(1M) every night and if any erroneous entries are
  33.      found, they are repaired and a report sent to the system administrator.
  34.      There are cases of corruption that _cccc_hhhh_kkkk_uuuu_tttt_eeee_nnnn_tttt cannot correct - in this case
  35.      a message is printed with the word _C_O_R_R_U_P_T, and _cccc_hhhh_kkkk_uuuu_tttt_eeee_nnnn_tttt terminates
  36.      without any further actions.
  37.  
  38.      If an administrator gets messages from _cccc_hhhh_kkkk_uuuu_tttt_eeee_nnnn_tttt frequently they may wish
  39.      to start an investigation into which program(s) on the machine are
  40.      generating them.  Infrequent messages can safely be ignored.
  41.  
  42.      The following is a list of messages and probable causes:
  43.  
  44.      _c_h_k_u_t_e_n_t:_E_R_R_O_R:_w_r_i_t_e _f_a_i_l_e_d _o_n:_x_x
  45.                The write to the _u_t_m_p_x file to correct a duplicate entry
  46.                failed.  This is likely due to an out of space condition on the
  47.                file system that contains the _u_t_m_p_x file.
  48.  
  49.      _c_h_k_u_t_e_n_t:_u_t_m_p_x _f_i_l_e _x_x _C_O_R_R_U_P_T _w_i_t_h _d_u_p _e_n_t_r_y _a_n_d _n_e_i_t_h_e_r _e_n_t_r_y `_D_E_A_D'
  50.                There is a duplicate entry (two entries with the same `id') but
  51.                _cccc_hhhh_kkkk_uuuu_tttt_eeee_nnnn_tttt didn't know how to fix it since both entries claim to
  52.                represent still existing sessions.  Action to correct this
  53.                problem should be taken promptly.  Having everyone log out and
  54.                then running _cccc_hhhh_kkkk_uuuu_tttt_eeee_nnnn_tttt will usually work.  Otherwise, the _uuuu_tttt_mmmm_pppp
  55.                and _uuuu_tttt_mmmm_pppp_xxxx files should be made zero length and the system
  56.                rebooted.
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. cccchhhhkkkkuuuutttteeeennnntttt((((1111MMMM))))                                                      cccchhhhkkkkuuuutttteeeennnntttt((((1111MMMM))))
  71.  
  72.  
  73.  
  74.      _c_h_k_u_t_e_n_t:_E_R_R_O_R:_C_o_u_l_d _n_o_t _u_p_d_a_t_e _u_t_m_p_x _f_i_l_e
  75.                The call to _pppp_uuuu_tttt_uuuu_tttt_xxxx_llll_iiii_nnnn_eeee(3) failed.  This is usually due to
  76.                either an out of space problem or that the _u_t_m_p file
  77.                corresponding to the _u_t_m_p_x file doesn't exist.  It is important
  78.                that both files exist - it is sufficient to simply _tttt_oooo_uuuu_cccc_hhhh(1) the
  79.                missing file.
  80.  
  81.      _u_t_m_p_x _f_i_x - _x_x _x_x _x_x _x_x - _s_e_e _c_h_k_u_t_e_n_t(_1_M)
  82.                This is `normal' message printed each time _cccc_hhhh_kkkk_uuuu_tttt_eeee_nnnn_tttt finds an
  83.                entry that represents a stale session.  If no other error
  84.                message are printed, it can be assumed that this entry was
  85.                fixed.
  86.  
  87.      _u_t_m_p_x _d_u_p - _x_x _x_x _x_x _x_x - _s_e_e _c_h_k_u_t_e_n_t(_1_M)
  88.                This message printed each time _cccc_hhhh_kkkk_uuuu_tttt_eeee_nnnn_tttt finds a duplicate
  89.                entry.  This represents a serious corruption of the _u_t_m_p_x file.
  90.                If this kind of corruption is frequently seen it is imperative
  91.                that the offending program(s) be tracked down and fixed.  If no
  92.                other error message are printed, it can be assumed that this
  93.                entry was fixed.
  94.  
  95.      The _cccc_hhhh_kkkk_uuuu_tttt_eeee_nnnn_tttt program may be run at any time by an administrator.
  96.      _cccc_hhhh_kkkk_uuuu_tttt_eeee_nnnn_tttt does take an optional _----_ffff _u_t_m_p_x-_f_i_l_e argument to let it operate
  97.      on any _u_t_m_p_x-like file.  Similarly, the optional _----_wwww _w_t_m_p_x-_f_i_l_e argument
  98.      instructs _cccc_hhhh_kkkk_uuuu_tttt_eeee_nnnn_tttt to operate on the given file when updating the _w_t_m_p
  99.      records.  If the _----_ffff option is given without the _----_wwww option, no _w_t_m_p
  100.      processing is done.
  101.  
  102. FFFFIIIILLLLEEEESSSS
  103.      _////_vvvv_aaaa_rrrr_////_aaaa_dddd_mmmm_////_uuuu_tttt_mmmm_pppp
  104.      _////_vvvv_aaaa_rrrr_////_aaaa_dddd_mmmm_////_uuuu_tttt_mmmm_pppp_xxxx
  105.      _////_vvvv_aaaa_rrrr_////_aaaa_dddd_mmmm_////_wwww_tttt_mmmm_pppp
  106.      _////_vvvv_aaaa_rrrr_////_aaaa_dddd_mmmm_////_wwww_tttt_mmmm_pppp_xxxx
  107.  
  108. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  109.      _gggg_eeee_tttt_uuuu_tttt_xxxx(3C)
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.